Add Testing Markdown Documentation for Standalone Detailed Inspection#25
Merged
Merged
Conversation
Change file to .md
wangz539
changed the title
…yproject.toml - Added available options for the CLI command, including `--seed` and `--force_rebuild`. - Expanded the input validation section to cover common errors and solutions. - Included details on overriding default inputs and customizing static tables.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds the guide for users who need to validate their own ATC-138 MATLAB vs. Python results using the standalone comparison engine (
compare_runs.py) and explains the metrics used in ATC-138.Contents
ICSB,HaseltonRCMF_4story)Motivation
While the current repo includes integration tests, this doc provides more detailed instructions for users who need to validate their own models outside of the testing framework. The metrics we use for the published version are also explained.